From: "Eckhard Maaß" <eckhard.s.maass@googlemail.com>
To: Bryan Turner <bturner@atlassian.com>
Cc: Junio C Hamano <gitster@pobox.com>,
Eric Kulcyk <Eric.kulcyk@microsoft.com>,
"git@vger.kernel.org" <git@vger.kernel.org>
Subject: Re: Tracking parent branches in Git
Date: Mon, 1 Jul 2019 22:40:17 +0200 [thread overview]
Message-ID: <20190701204017.GA7537@esm> (raw)
In-Reply-To: <CAGyf7-EBs_cRB5R7RyQhX0ZDNqLZWVJEYEtqkGRGJykRqKKTvA@mail.gmail.com>
On Mon, Jul 01, 2019 at 12:48:16PM -0700, Bryan Turner wrote:
> Since branches are ephemeral names and have no intrinsic metadata of
> their own (unlike, say, annotated tags or commits), I suspect
> implementing something like this may be more complicated than it might
> initially appear, especially if said metadata needs to be communicated
> to remote repositories (which implies it might require changes to the
> wire protocol as well).
You can right now give meta data of your choice with --push-option to
the push command. The Gerrit system makes use of that already. However,
this would not be intrinsic to Git, but the serve needs to react on
those options. And it should be in good company with suitable client
tools.
Take care,
Eckhard
next prev parent reply other threads:[~2019-07-01 20:40 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-01 18:50 Tracking parent branches in Git Eric Kulcyk
2019-07-01 19:34 ` Junio C Hamano
2019-07-01 19:48 ` Bryan Turner
2019-07-01 20:12 ` rsbecker
2019-07-02 9:23 ` Philip Oakley
2019-07-02 17:36 ` Junio C Hamano
2019-07-02 18:52 ` Bryan Turner
2019-07-02 19:24 ` Theodore Ts'o
2019-07-03 15:58 ` Philip Oakley
2019-07-01 20:40 ` Eckhard Maaß [this message]
2019-07-01 20:58 ` Eric Kulcyk
2019-07-01 21:04 ` Eric Kulcyk
2019-07-02 6:42 ` Andreas Krey
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=20190701204017.GA7537@esm \
--to=eckhard.s.maass@googlemail.com \
--cc=Eric.kulcyk@microsoft.com \
--cc=bturner@atlassian.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.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 NNTP newsgroup(s).