public inbox for archer@sourceware.org
 help / color / mirror / Atom feed
From: Pedro Alves <palves@redhat.com>
To: Jan Kratochvil <jan.kratochvil@redhat.com>
Cc: Tom Tromey <tromey@redhat.com>, Project Archer <archer@sourceware.org>
Subject: Re: Proposal to change branch maintenance
Date: Wed, 13 Feb 2013 12:33:00 -0000	[thread overview]
Message-ID: <511B8800.8040801@redhat.com> (raw)
In-Reply-To: <20130213121556.GA21353@host2.jankratochvil.net>

On 02/13/2013 12:15 PM, Jan Kratochvil wrote:
>> > I think newer git even has some automated thing for documenting
>> > branches, but unfortunately I think we aren't all on a new-enough git
>> > yet.  We could adopt that when we're ready.
> ... you probably mean "git branch --edit-description", I do not know it.
> It exists even in the oldest supported Fedora (F-17) and in reality archer.git
> is not in use outside of RH so I do not see a problem with --edit-description.

AFAIK, that's only stored in the local ".git/config", not put on the server...

-- 
Pedro Alves

  reply	other threads:[~2013-02-13 12:33 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-02-11 21:56 Tom Tromey
2013-02-13 11:32 ` Gary Benson
2013-02-13 12:16 ` Jan Kratochvil
2013-02-13 12:33   ` Pedro Alves [this message]
2013-02-13 12:53   ` Gary Benson
2013-02-18 16:10   ` Tom Tromey
2013-02-18 16:20     ` Jan Kratochvil
2013-02-18 16:29       ` Tom Tromey
2013-02-18 17:03         ` Jan Kratochvil
2013-02-18 17:40           ` Tom Tromey
2013-02-18 22:01           ` Tom Tromey
2013-02-22 15:54             ` Tom Tromey
2013-02-26 17:33     ` Tom Tromey
2013-02-26 20:13       ` Tom Tromey
2013-02-26 20:31         ` Sergio Durigan Junior
2013-02-27 20:50           ` Tom Tromey
2013-02-27 20:50         ` Tom Tromey
2013-02-27 21:15           ` Tom Tromey
2013-02-18 11:46 ` Sergio Durigan Junior
2013-02-18 16:11   ` Tom Tromey
2013-02-18 16:16     ` Jan Kratochvil
2013-02-22 15:06       ` Tom Tromey
2013-02-22 21:27 ` Tom Tromey

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=511B8800.8040801@redhat.com \
    --to=palves@redhat.com \
    --cc=archer@sourceware.org \
    --cc=jan.kratochvil@redhat.com \
    --cc=tromey@redhat.com \
    /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 read-only IMAP folder(s) and NNTP newsgroup(s).