Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Grant Edwards <grant.b.edwards@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] OT: git workflow question
Date: Wed, 16 Dec 2009 16:53:24 +0000 (UTC)	[thread overview]
Message-ID: <hgb3a3$88l$1@ger.gmane.org> (raw)

I don't seem to "get" git when it comes to working with
buildroot.

 1) I cloned the repository about two weeks ago

 2) I made a bunch of small edits to docs/buildroot.html and
    commited them locally.

 3) I submitted the changes using git format-patch

 4) The patches were merged to the "master" repository

 5) Then when I did a "git pull" to update my repository, it
    failed because of conflicts in docs/buildroot.html

Since I had only changed the one file (and those changes had
been merged into the master repository) I didn't bother trying
to resolve the conflict -- I just blew away my repository and
did a 'clone'.

Here's my question: why was there a conflict?

Is this how git is supposed to work?

-- 
Grant Edwards                   grante             Yow! I'm ZIPPY the PINHEAD
                                  at               and I'm totally committed
                               visi.com            to the festive mode.

             reply	other threads:[~2009-12-16 16:53 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-12-16 16:53 Grant Edwards [this message]
2009-12-16 19:37 ` [Buildroot] OT: git workflow question Thomas Petazzoni
2009-12-16 20:05   ` Grant Edwards
2009-12-16 20:20     ` Peter Korsgaard
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='hgb3a3$88l$1@ger.gmane.org' \
    --to=grant.b.edwards@gmail.com \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox