https://groups.google.com/forum/#!topic/git-users/nzwVr5li3cM
> Tom Roche
> How to restrict the commit history or messages that get pushed to a remote
> repository?
...
> Gergely Polonkai
...
> git rebase -i[.] Before pushing, rebase on the last public commit, and
&g
ond repo to the public remote
This seems painful, and maybe that's what Fred deserves. But I'm wondering, is
there a way to accomplish Fred's objective more easily?
TIA, Tom Roche
--
You received this message because you are subscribed to the Google Groups "Git
for human
Tom Roche Monday, May 7, 2012 10:09:29 AM UTC-7
>> How to [easily] overwrite managed files in an existing directory
>> with the latest versions from a remote branch/repo, without merging
>> or whack-n-clone?
as defined @ top of thread
https://groups.google.com/d/topic/git
ich must be saved and then restored.
I'm wondering: is there another way to do this?
TIA, Tom Roche
--
You received this message because you are subscribed to the Google Groups "Git
for human beings" group.
To post to this group, send email to git-users@googlegroups.
s would maintain a separate repository on one or both of
the clusters. Branch=master would, at any given time, hold the latest release
or integration build. Immediately before a release or integration is declared
(only following its successful testing!), the current contents of branch=master
would
e history
* need to do a lot of merging
? Or am I thinking wrong, and should do Something Completely Different?
TIA, Tom Roche
--
You received this message because you are subscribed to the Google Groups "Git
for human beings" group.
To post to this group, send email to git-users
it users on the cluster so that
git protocol will use port=443 automagically? Should this be done
via git (e.g., using `git remote` or `git config`)? or via ssh
(e.g., using ~/.ssh/config), or some other way?
TIA, Tom Roche
--
You received this message because you are subscribed to the Google Gro
