From: Rod Whitby <rod@whitby.id.au>
To: openembedded-devel@lists.openembedded.org
Subject: Re: ETA on git conversion
Date: Thu, 09 Oct 2008 10:17:07 +1030 [thread overview]
Message-ID: <48ED467B.5080208@whitby.id.au> (raw)
In-Reply-To: <200810081757.57676.zecke@selfish.org>
Holger Freyther wrote:
> On Wednesday 08 October 2008 13:18:16 Koen Kooi wrote:
>
>> The old wiki had one, dunno if the new wiki overlords decided to move it
>> to the new wiki. Ask them.
>
> http://wiki.openembedded.net/index.php/GitPhraseBook
>
> is this any good?
Some comments (open for discussion before I change the wiki page):
> git clone git://git.openembedded.net/FIXME openembedded.git
Does it need to create openembedded.git as the directory name rather
than just openembedded?
> git config user.name "Your Name"
> git config user.mail "you@name"
Do we want to use the --global flag so that the scope of these commands
covers all git repos for that user and they don't forget to do it for
every new repo they clone?
> git commit --amend
Add a comment that this should only be done on commits that have not
been pushed anywhere, and should *never* be done on commits that have
been pushed to a public repo?
BTW, the git commands that I've been using for FSO work can be found in
the FSO Makefile at http://downloads.freesmartphone.org/Makefile
In particular, this is how I clone the OE trial git repo:
> .PHONY: setup-openembedded
> .PRECIOUS: openembedded/.git/config
> setup-openembedded openembedded/.git/config:
> [ -e openembedded/.git/config ] || \
> ( git clone git://git.openembedded.net/org.openembedded.dev openembedded ; \
> cd openembedded ; \
> git config --add remote.origin.fetch '+refs/remotes/*:refs/remotes/*' )
> ( cd openembedded && \
> ( git branch | egrep -e ' org.openembedded.dev$$' > /dev/null || \
> git checkout -b org.openembedded.dev --track origin/org.openembedded.dev ))
> ( cd openembedded && git checkout org.openembedded.dev )
> touch openembedded/.git/config
Comments on that strategy are welcome.
Generic prejudices about Makefiles are not :-)
-- Rod
next prev parent reply other threads:[~2008-10-08 23:51 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-08 5:51 ETA on git conversion Holger Freyther
2008-10-08 7:10 ` Khem Raj
2008-10-08 7:31 ` Tom Rini
2008-10-08 8:07 ` Koen Kooi
2008-10-08 10:52 ` Philip Balister
2008-10-08 10:56 ` Michael Krelin
2008-10-08 11:03 ` Holger Freyther
2008-10-08 11:18 ` Koen Kooi
2008-10-08 13:19 ` Leon Woestenberg
2008-10-08 13:32 ` Philip Balister
2008-10-08 15:57 ` Holger Freyther
2008-10-08 16:51 ` Michael Krelin
2008-10-08 16:54 ` Koen Kooi
2008-10-08 18:05 ` Philip Balister
2008-10-08 23:47 ` Rod Whitby [this message]
2008-10-09 9:39 ` git and branches Sledz, Steffen
2008-10-09 20:37 ` Denys Dmytriyenko
2008-10-09 22:31 ` Rod Whitby
2008-10-14 14:41 ` ETA on git conversion Jonas Bonn
2008-10-08 10:10 ` Marcin Juszkiewicz
2008-10-08 10:17 ` Koen Kooi
2008-10-08 13:06 ` Otavio Salvador
2008-10-14 14:12 ` Holger Freyther
2008-10-14 21:41 ` Holger Freyther
2008-10-15 0:29 ` Rodrigo Vivi
2008-10-15 2:17 ` Rod Whitby
2008-10-15 2:30 ` Rod Whitby
2008-10-15 9:31 ` Uli Luckas
2008-10-15 14:14 ` Mark Brown
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=48ED467B.5080208@whitby.id.au \
--to=rod@whitby.id.au \
--cc=openembedded-devel@lists.openembedded.org \
/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.