On Thu, Nov 20, 2008 at 9:58 AM, Eric Kow <[EMAIL PROTECTED]> wrote: > > In the future, do keep the new darcs send --in-reply-to in mind :-) > > Maybe we can update the docs to encourage more users to take advantage > of it. This makes it easier for the maintainer to know what is the > latest version of each patch and for people looking at the archives to > understand the flow, i.e. what happened to a patch that got sent.
Personally, I don't plan to use --in-reply-to due to the overhead and the error proneness aspects. I have to first locate the thread, then to get the message-id I have to ask my email client to show me the raw text of the email, find that particular header bit, get it into the clipboard and then insert it into my command line correctly quoted. Then after I do all that, my client still won't thread the message for me if the subject of the new patch bundle is different from the old one. > We still could use a patch tracker, but this is a useful partial > substitute in the meantime. I would prefer that. github seems to handle this rather elegantly. Just my $0.02, Jason _______________________________________________ darcs-users mailing list [email protected] http://lists.osuosl.org/mailman/listinfo/darcs-users
