Re: bzr issues

On Thu, Apr 3, 2008 at 12:22 AM, Alex Rousskov
<rousskov@measurement-factory.com> wrote:
>
> On Thu, 2008-04-03 at 08:55 +1100, Robert Collins wrote:
> > On Wed, 2008-04-02 at 15:52 -0600, Alex Rousskov wrote:
> > > On Thu, 2008-04-03 at 08:38 +1100, Robert Collins wrote:
> > > > On Wed, 2008-04-02 at 11:21 -0600, Alex Rousskov wrote:
> > > >
> > > > > I think an incomplete "[MERGE] " default subject would be much better
> > > > > that the current behavior that will lead to _incorrect_ subjects.
> > > > >
> > > > > In addition, a command line option to specify the subject should be
> > > > > added.
> > > >
> > > > Amos wasn't entirely clear in his initial report. What is happening is
> > > > that bzr send when there is no detected desktop mail client is providing
> > > > a text editor window with *no* facility for setting the subject.
> > > >
> > > > This is clearly a usability bug, and once fixed the issue will go away.
> > > > There is a bug open on this now.
> > >
> > > The second bug is that the default subject for desktop mail clients is
> > > wrong.
> >
> > You want just [MERGE] right ?
>
> This is something that bzr developers should decide.
>
> IMHO, "[MERGE] " or "[MERGE] PUT SUBJECT HERE" or even "[MERGE] PUT
> SUBJECT HERE <unique ID>" may work, I guess.
>
> The [MERGE] prefix seems to be needed because otherwise most folks will
> not know it is required for integration with other tools. However, if
> those tools differ in their requirements or often not used, then an
> empty subject is the best solution (some mailers will warn about it
> even).

IMO integration with other tools should use out-of-band information,
such as an extra mail header.
[MERGE] in the subject is good to interact with humans, but too flimsy
to be used with automated tools.

-- 
 /kinkie