|
I've got a project (under git) I'd like to release, but without it's entire history. I basically want to release just the last few commits publically. What's the best way to do this while still maintaining the history privately?
|
| # ¿ Jun 1, 2010 01:05 |
|
|
|
| # ¿ May 21, 2013 09:31 |
|
|
that was just the git server daemon, the thing that listens for remote git requests. github abandoned it, but andrew thompson wrote a blog series on optimizing it and got hired by basho as a result.
|
| # ¿ Aug 20, 2011 05:30 |
|
|
Optimus Prime Ribs posted:When I do git add foo.py does that just mean "add this to the list of items that will be commited" and nothing else? There's three 'sections' active when using git, your working set, the stage and the repository. The working set is the current set of files, just as they appear on disk. The repository is a series of snapshots you can check out (potentially overwriting) to the working set. The stage is a set of changes that can be written to a new snapshot in the repository. Adding a file writes the state of the file at the time add is run to the stage. This means if you add foo to the stage, then edit foo, none of those edits will make it into the commit unless you readd the file.
|
| # ¿ May 8, 2012 20:47 |
|
