git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Wincent Colaiuta <win@wincent.com>
To: Eric LEBIGOT <Eric.Lebigot@normalesup.org>
Cc: git@vger.kernel.org
Subject: Re: Is it possible to have a file shared between branches?
Date: Mon, 12 Apr 2010 11:36:16 +0200	[thread overview]
Message-ID: <95BBC559-1EDC-4BF8-98A2-05729BFCCA1D@wincent.com> (raw)
In-Reply-To: <alpine.OSX.2.01.1004121058390.52293@kroll.spectro.jussieu.fr>

El 12/04/2010, a las 11:10, Eric LEBIGOT escribió:

> Hello,
> 
> Is it possible for git to track a single file that would be shared accross branches?  Case in point: a to-do list file that describes what has to be done in all the branches; it can be convenient to put all the things that have to be done in a single, shared file, while keeping this to-do list in sync with the code (so that it lists what has been done, and what remains to be done).  Committing in a branch would in effect also commit the shared file in the other branches (another possibility may be to have in effect many "trees" in a single git directory, with a specific tree for the to-do list).
> 
> Is this something git can do?

Not exactly.

The way I'd do this is to put that kind of "meta" file in a branch of its own.

Look at the git.git repo itself for an example of a repo with a few branches (todo, html, and man) that are independent of the actual development branches (master, maint, next, pu).

Cheers,
Wincent

  parent reply	other threads:[~2010-04-12  9:52 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 [this message]
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

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=95BBC559-1EDC-4BF8-98A2-05729BFCCA1D@wincent.com \
    --to=win@wincent.com \
    --cc=Eric.Lebigot@normalesup.org \
    --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;
as well as URLs for NNTP newsgroup(s).