Thread (4 messages) flat view 4 messages, 2 authors, 2016-06-15

Re: I never want to push a given change

From: nathan bullock <hidden>
Date: 2016-06-15 22:43:21

On 7/16/07, Brian Gernhardt [off-list ref] wrote:
On Jul 16, 2007, at 12:18 PM, nathan bullock wrote:
quoted
I have been using git for a little while and one thing that I would
like to
be able to do is never push a given change, or set of changes.

So lets say I clone a .git repository. Then I make a couple of changes
that I don't want anyone else to see, do a commit. Then I make some
other changes that I want everyone else to see and do another commit.

How do I push just the second commit?
And how do I make it so that every other time I do a push after
this that
first commit will never be sent?
Generally the way I do such things is multiple branches.  Have a
branch "local" (or a more descriptive name) that isn't pushed out
anywhere.  Place any changes you do NOT want shared on that brach.
Place changes to be shared on the master or appropriate topic
branch.  Instead of committing changes to be shared on top of the
local ones, use "git rebase" to keep the local branch on top of the
shared ones.
Ahhh, thanks for that. You forced me to go stare at the git rebase documentation
until I actually understood what it does. It looks like that will work
perfectly.

Nathan
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help