From: "Arnaud Lacombe" <lacombar@gmail.com>
To: "Miklos Vajna" <vmiklos@frugalware.org>
Cc: "Junio C Hamano" <gitster@pobox.com>,
"Karl Chen" <quarl@cs.berkeley.edu>,
"David Aguilar" <davvid@gmail.com>,
"Git mailing list" <git@vger.kernel.org>
Subject: Re: git-rev-parse --symbolic-abbrev-name
Date: Mon, 5 Jan 2009 00:35:23 -0500 [thread overview]
Message-ID: <1a69a9d80901042135w5f1c4aa2jd56ff1d9e4ffd38a@mail.gmail.com> (raw)
In-Reply-To: <20090104223819.GI21154@genesis.frugalware.org>
Hi,
On Sun, Jan 4, 2009 at 5:38 PM, Miklos Vajna <vmiklos@frugalware.org> wrote:
> On Sun, Jan 04, 2009 at 03:23:03PM -0500, Arnaud Lacombe <lacombar@gmail.com> wrote:
>> ps: I choose --symbolic-short-name as the opposite of
>> --symbolic-full-name for consistency.
>> ps2: sorry for the bogus mime-type
>
> That's not a problem, just don't attach your patch. Please read
> Documentation/SubmittingPatches.
>
ok, looks, I did these patch this morning quickly, didn't commit
anything or so. If there worth anything, then I'll spent time
commiting, doing nice integration, documentation, whatsoever ... Just
need a quick yes or no, these as patch are really trivial.
- Arnaud
ps: btw, Documentation/git-format-patch.txt does not describe the -M
flag, not does it describe the -B flag
next prev parent reply other threads:[~2009-01-05 5:36 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-02 3:28 git-branch --print-current Karl Chen
2009-01-02 4:26 ` David Aguilar
2009-01-04 2:18 ` Karl Chen
2009-01-04 3:38 ` Miklos Vajna
2009-01-04 4:26 ` Karl Chen
2009-01-04 5:17 ` Junio C Hamano
2009-01-04 12:34 ` git-rev-parse --symbolic-abbrev-name [was Re: git-branch --print-current] Karl Chen
2009-01-04 12:40 ` demerphq
2009-01-04 19:36 ` git-rev-parse --symbolic-abbrev-name Junio C Hamano
2009-01-04 20:23 ` Arnaud Lacombe
2009-01-04 22:38 ` Miklos Vajna
2009-01-05 5:35 ` Arnaud Lacombe [this message]
2009-01-05 6:45 ` Miklos Vajna
2009-01-06 8:18 ` Junio C Hamano
2009-01-07 4:58 ` Arnaud Lacombe
2009-01-04 13:35 ` git-branch --print-current demerphq
2009-01-05 0:41 ` Junio C Hamano
2009-01-05 2:18 ` Shawn O. Pearce
2009-01-05 3:55 ` Junio C Hamano
2009-01-05 5:50 ` Jeff King
2009-01-04 8:21 ` Arnaud Lacombe
2009-01-04 12:40 ` Karl Chen
2009-01-04 12:49 ` demerphq
2009-01-04 17:55 ` Arnaud Lacombe
2009-01-04 18:02 ` Adeodato Simó
2009-01-04 21:48 ` Jakub Narebski
2009-01-04 10:07 ` Alexandre Dulaunoy
2009-01-04 12:31 ` demerphq
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=1a69a9d80901042135w5f1c4aa2jd56ff1d9e4ffd38a@mail.gmail.com \
--to=lacombar@gmail.com \
--cc=davvid@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=quarl@cs.berkeley.edu \
--cc=vmiklos@frugalware.org \
/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).