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

Re: avoiding committing personal cruft

From
David <wizzardx@gmail.com>
Date
Jun 21, 2008, 15:53 UTC
Message-ID
<18c1e6480806210853k72274173gaaeb11dd7991c8ed@mail.gmail.com>
In-Reply-To
<e5e204700806210620m35fce27eh8eddaf7cb68f1986@mail.gmail.com>
On Sat, Jun 21, 2008 at 3:20 PM, James Sadler <freshtonic@gmail.com> wrote:
Show 12 quoted lines
>
> The ide-branch has nothing in it except the cruft from the IDE and the
> paths leading up to that cruft.
> The master branch has a .gitignore that ignores the IDE files so I
> won't end up polluting master by accident.
>
> It's a manageable solution for now.  I tend to think of it
> conceptually as 'layering' two branches: I want the
> content of both present in the working tree.
>
> I was just wondering if anyone else has tried something similar.
>

Sounds like a normal use of topic branches. Branches rebased against master, where you you keep changes you don't want to go into the main branch at this time.

David.
Previous: James SadlerNext: David
Message 2 of 3 in “avoiding committing personal cruft”
  1. James SadlerJun 21, 2008
  2. DavidJun 21, 2008
  3. DavidJun 22, 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.