git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: Eric LEBIGOT <Eric.Lebigot@normalesup.org>
Cc: Jakub Narebski <jnareb@gmail.com>, git@vger.kernel.org
Subject: Re: Is it possible to have a file shared between branches?
Date: Mon, 12 Apr 2010 09:10:11 -0700	[thread overview]
Message-ID: <7vd3y4lkik.fsf@alter.siamese.dyndns.org> (raw)
In-Reply-To: <alpine.OSX.2.01.1004121639230.60420@kroll.spectro.jussieu.fr> (Eric LEBIGOT's message of "Mon\, 12 Apr 2010 16\:46\:11 +0200 \(CEST\)")

Eric LEBIGOT <Eric.Lebigot@normalesup.org> writes:

> Thank you!  I can see what is done in the git.git repository, thanks
> to your pointer, and it looks like I'm trying to get from git.  But
> how do you create and manage such an independent 'todo' branch?  This
> branch appears on the same level as master, in the pages you gave, but
> you also mention a "non versioned Meta/ directory".  Does this mean
> that the file structure is like the following?
>
>  ./.git
>  Meta/.git
>  Meta/<todo files>
>
> If yes, how do all branches appear at the same level in
> http://git.kernel.org/?p=git/git.git;a=summary ?  If no, how was the
> todo' branch created?  (I would love to have the todo file in the same
> directory as the rest.)

The way this was arranged was simply:

	$ mkdir Meta
        $ cd Meta && git init
        $ do a lot of work that creates files you see on 'todo'
        $ git commit
        $ git push k.org:/pub/scm/git/git.git master:todo
	$ cd .. ;# back to the primary working tree.

And the last step could have been to push into /pub/scm/git/git-todo.git/
iow a separate repository.

The _only_ reason 'todo' and 'master' live in the same repository is
because I only have write privilege to /pub/scm/git/git.git/ and not at
the /pub/scm/git/ level.  Having these unrelated branches in the same
repository is nothing to find cool and imitate; I'd recommend not to do it
if you don't have to.

Having these unrelated branches published in the same repository helps
distribution a bit, but it never helps the use of the contents in these
branches.

      parent reply	other threads:[~2010-04-12 16:10 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-04-12  9:10 Is it possible to have a file shared between branches? Eric LEBIGOT
2010-04-12  9:33 ` Ævar Arnfjörð Bjarmason
2010-04-12  9:36 ` Wincent Colaiuta
2010-04-12 10:07 ` Jakub Narebski
2010-04-12 14:46   ` Eric LEBIGOT
2010-04-12 15:06     ` Wincent Colaiuta
2010-04-12 16:10     ` Junio C Hamano [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=7vd3y4lkik.fsf@alter.siamese.dyndns.org \
    --to=gitster@pobox.com \
    --cc=Eric.Lebigot@normalesup.org \
    --cc=git@vger.kernel.org \
    --cc=jnareb@gmail.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).