[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [ecf-dev] Move to GIT
- From: Wim Jongman <wim.jongman@xxxxxxxxx>
- Date: Wed, 16 Jun 2010 23:02:20 +0200
- Delivered-to: email@example.com
- Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:from:to:in-reply-to:content-type :content-transfer-encoding:x-mailer:mime-version:subject:date :references; b=xYqX2ayGPsDAe3oPvOoVXwiP2XgEd08Emxr1VUA3HeFbf41Ska8mnnACqTZwRDFJZM iK62gHf5ZamqjT5TznrgxRyKbSSkJlRF+FjX6fF+h9SS9QQvFZD8XJ4zJ4jlmOUVTWZr rLPtGJqIaNtLh7teiJPYGRWJhsy97GvzKCg5Q=
Suppose you and I have copies of the same "master". Instead of
directly updating back into the master, we decide to fill an
itermediate place first (TEST). Would it be more difficult to push it
in a branch as opposed to a repository?
On Jun 16, 2010, at 22:44, Chris Aniszczyk <caniszczyk@xxxxxxxxx> wrote:
On Wed, Jun 16, 2010 at 3:37 PM, Wim Jongman <wim.jongman@xxxxxxxxx>
I guess that could work as well. If a change never makes it to
guess it should be reverted at some point. I have no idea how
is with Git.
git rebase or filter branch, not that hard.
A branch would be the preferred way imho.
+1 860 839 2465
ecf-dev mailing list