From: Jakub Narebski <jnareb@gmail.com>
To: git@vger.kernel.org
Subject: Branch metainformation
Date: Thu, 20 Apr 2006 09:39:09 +0200 [thread overview]
Message-ID: <e27dqv$u6f$1@sea.gmane.org> (raw)
It seems that ever so often there is question posted on this list on which
the answer is to add '+' in 'pu' branch 'Pull:' line. I think that it is
not a good policy to have puller to remember which branches can be
fast-forwarded, and which needs to be merged. It should be an information
set and stored by person managing the branch (pullee), as some kind of
metainformation for the branch (like description and optional signature is
for tags).
Perhaps then there would be a place for short, one-line description of the
branch...
--
Jakub Narebski
Warsaw, Poland
next reply other threads:[~2006-04-20 7:39 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-20 7:39 Jakub Narebski [this message]
2006-04-20 9:37 ` Branch metainformation Johannes Schindelin
2006-04-20 10:18 ` Junio C Hamano
2006-04-20 11:41 ` Johannes Schindelin
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='e27dqv$u6f$1@sea.gmane.org' \
--to=jnareb@gmail.com \
--cc=git@vger.kernel.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