From: Sam Vilain <sam@vilain.net>
To: Eric Wong <normalperson@yhbt.net>
Cc: Avishay Lavie <avishay.lavie@gmail.com>,
git@vger.kernel.org, Bryan Jacobs <bjacobs@woti.com>
Subject: Re: [spf:guess] Re: [PATCH] git svn dcommit: avoid self-referential mergeinfo lines when svn.pushmergeinfo is configured
Date: Thu, 15 Mar 2012 15:28:56 -0700 [thread overview]
Message-ID: <4F626D28.70100@vilain.net> (raw)
In-Reply-To: <20120315220242.GA9348@dcvr.yhbt.net>
On 3/15/12 3:02 PM, Eric Wong wrote:
> Avishay Lavie<avishay.lavie@gmail.com> wrote:
>> [PATCH] git svn dcommit: avoid self-referential mergeinfo lines when
>> svn.pushmergeinfo flag is configured
>
> Subject line is too long, ~50 chars is the limit.
> See git-commit(1) / Documentation/SubmittingPatches
Can I suggest:
git svn dcommit: avoid self-referential mergeinfo
prev parent reply other threads:[~2012-03-15 22:29 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-14 16:09 [PATCH] git svn dcommit: avoid self-referential mergeinfo lines when svn.pushmergeinfo is configured Avishay Lavie
2012-03-14 16:15 ` Bryan Jacobs
2012-03-14 16:23 ` Thomas Rast
2012-03-15 22:02 ` Eric Wong
2012-03-15 22:07 ` Bryan Jacobs
2012-03-15 22:28 ` Sam Vilain [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4F626D28.70100@vilain.net \
--to=sam@vilain.net \
--cc=avishay.lavie@gmail.com \
--cc=bjacobs@woti.com \
--cc=git@vger.kernel.org \
--cc=normalperson@yhbt.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).