git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: Multiple working trees with GIT ?

From
JFJ. Bruce Fields <bfields@fieldses.org>
Date
Jan 24, 2008, 14:51 UTC
Message-ID
<20080124145128.GA26164@fieldses.org>
In-Reply-To
<20080124074952.GA8793@1wt.eu>
On Thu, Jan 24, 2008 at 08:49:52AM +0100, Willy Tarreau wrote:
Show 17 quoted lines
> Hi all,
> 
> I'm having long thoughts about how to use GIT to manage a distro. One of
> the aspects which comes very often is the notion of "variant" for a
> packaging. For instance, the whole project could consist in a list of packages
> with their branches, but this list may vary depending on the platform, the
> medium, etc... I was searching how to propagate common changes withing variants
> with the least hassle.
> 
> I figured out that having one file list per variant will be very annoying. In
> another project, that's already what I have and frankly, applying the same
> change to 10 files is counter-productive. Since the lists will often be the
> sames except for a few entries, and since most updates will be relevant to
> all variants, I thought branches will be my best friends.
> 
> But I would like to be able to always access file lists, without having to
> constantly git-checkout <variant-X>.
Could just read-only access with git-show be enough for your purposes?:
	git show <branch-name>:		# show top-level directory,
	git show <branch-name>:lib/	# show lib/ directory, etc....
	git show <branch-name>:lib/Makefile
--b.
Previous: Willy Tarreau
Message 8 of 8 in “Multiple working trees with GIT ?”
  1. Willy TarreauJan 24, 2008
  2. Julian PhillipsJan 24, 2008
  3. Johannes SchindelinJan 24, 2008
  4. Willy TarreauJan 24, 2008
  5. Johannes SchindelinJan 24, 2008
  6. Willy TarreauJan 24, 2008
  7. Willy TarreauJan 24, 2008
  8. J. Bruce FieldsJan 24, 2008

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.