From: Peter Korsgaard <jacmet@uclibc.org>
To: buildroot@busybox.net
Subject: [Buildroot] OT: git workflow question
Date: Wed, 16 Dec 2009 21:20:06 +0100 [thread overview]
Message-ID: <87ocly658p.fsf@macbook.be.48ers.dk> (raw)
In-Reply-To: <hgbei7$jgr$2@ger.gmane.org> (Grant Edwards's message of "Wed, 16 Dec 2009 20:05:27 +0000 (UTC)")
>>>>> "Grant" == Grant Edwards <grant.b.edwards@gmail.com> writes:
Hi,
>> No. You should have made your changes in a separate branch
>> instead of a master branch.
Grant> Thanks. That's the clue I was missing. The tutorials I had
Grant> read on git didn't say that -- they showed all work being done
Grant> in the master branch.
That can work for quick edits, but then you need to remove the commit
before pulling updates in (git reset --hard origin/master).
I would recommend just creating a branch instead though as it's so
easy/fast to do in git (and it allows you to use git-rebase).
>> This is at least how I'm contributing to Buildroot. Not
>> necessarly the cleanest way, I'm no git expert.
Grant> I certainly sounds like a better approach that what I was doing.
And it's what I would consider the "normal" way of working (it's atleast
how I do it when I contribute something to a project using git).
--
Bye, Peter Korsgaard
next prev parent reply other threads:[~2009-12-16 20:20 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-16 16:53 [Buildroot] OT: git workflow question Grant Edwards
2009-12-16 19:37 ` Thomas Petazzoni
2009-12-16 20:05 ` Grant Edwards
2009-12-16 20:20 ` Peter Korsgaard [this message]
2009-12-16 20:06 ` Markus Heidelberg
2009-12-17 21:40 ` Julien Boibessot
2009-12-16 19:56 ` Chris Packham
2009-12-16 20:00 ` Markus Heidelberg
2009-12-16 20:03 ` Grant Edwards
[not found] <mailman.5919.1260994066.28478.buildroot@busybox.net>
2009-12-18 8:08 ` Vellemans, Noel
2009-12-18 12:04 ` Lionel Landwerlin
2009-12-18 14:22 ` Chris Packham
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87ocly658p.fsf@macbook.be.48ers.dk \
--to=jacmet@uclibc.org \
--cc=buildroot@busybox.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.