If you have multiple darcs repositories for which you receive darcs
patches, it would be nice if you could easily tell which repository
the patch is for.

Instead of 
 darcs patch: name of patch
 darcs patch: name of some other patch,

Something like
 darcs patch: [project foo] name of patch
 darcs patch: [project bar] name of some other patch

would make life a tiny bit easier.

I suppose the configuration for this would live in _darcs/prefs
(much like _darcs/prefs/email)

I'm sure there are possible refinements to this idea as well...

Eric Kow wrote:
> New submission from Eric Kow <kowey@darcs.net>:
> 
> If you have multiple darcs repositories for which you receive darcs
> patches, it would be nice if you could easily tell which repository
> the patch is for.
> 
> Instead of 
>  darcs patch: name of patch
>  darcs patch: name of some other patch,
> 
> Something like
>  darcs patch: [project foo] name of patch
>  darcs patch: [project bar] name of some other patch
> 
> would make life a tiny bit easier.

There is a header that ``darcs send`` includes in the patch mail already 
that tells you the repository the patch is sent to. For example:

DarcsURL: http://darcs.net/

Presumably one simple way to get what you seek is a small plugin to your 
preferred email client to get it to show that DarcsURL header somewhere 
you might better notice it.

Oh yeah!  I had not considered that.  

This could still be useful if patches go to mailing lists (because then you only
have to configure one thing and everybody benefits from it, instead of everybody
configuring their mail clients).  Also, in mail clients, it is typical to get a
summary of messages, showing the subject lines of all messages at a glance.

Making Darcs-URL more prominent will be useful for when you decide to view a
message, but it doesn't help much when you're looking at the message index
(unless you're willing to do some work to make darcs-url appear in the index,
which is likely possible in mutt).

Also, this sort of option would not require adding any new flags to darcs, just
a new preference file, which is not so bad.

Anyway, I won't be too bothered if this is marked wont-fix

I guess we might as well wont-fix this

The text of the mail messages that darcs send produces lists the patches (with
author, name, description). It does not mention the name or URL of the
repository the mails are sent to. This is unfortunate on mailing lists like
libraries or xmonad, where patches against multiple repos are sent in. One has
to guess by looking at the filenames _inside_ the diff to find out what repo the
patch is aimed for.

I suggest a line like "5 new patches for repository http:/....:" before the list
of patches in the mail body.

I brought msg9674 in from issue1722.

Joachim, please set this back to wont-fix if you think the DarcsURL header is
really good enough after all.

[For completeness, mentioning an alternative approach.]

I always assumed that when this became an issue, I'd do it this way:

    http://en.wikipedia.org/wiki/Email_address#Sub-addressing

Specifically, suppose you have three projects, "foo", "bar" and "baz".  Then

    echo "nurk+foo@example.net" >foo/_darcs/prefs/email
    echo "nurk+bar@example.net" >bar/_darcs/prefs/email
    echo "nurk+baz@example.net" >baz/_darcs/prefs/email

Now a "darcs send" against foo will be sent to nurk+foo.  It'll still
end up in the "nurk" inbox, but an MTA (e.g. postfix) or MDA
(maildrop, procmail) can be intelligent about which repository it
attempts to apply it to, per "Setting up a sendable repository using
procmail" in

    http://darcs.net/manual/node3.html#SECTION00355000000000000000

I guess even through sub-addresses support is now widespread, many
users' MUAs don't know how to filter based on them... You also
mentioned an existing X-DarcsURL field, which I guess is nearly as
easy for an MTA/MDA to work with.

The following patch updated the status of issue1362 to be resolved:

* Resolve issue1362: Mention repo name in mail send body 
Ignore-this: 3e5e0bbc5415b1b3d7c72ba3e8e077c8