public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Mike Frysinger <vapier@gentoo.org>
To: u-boot@lists.denx.de
Subject: [U-Boot] ATMEL Custodians == /dev/null ??
Date: Thu, 5 Aug 2010 12:16:13 -0400	[thread overview]
Message-ID: <201008051216.14165.vapier@gentoo.org> (raw)
In-Reply-To: <4C5A80E1.9050504@emk-elektronik.de>

On Thursday, August 05, 2010 05:14:09 Reinhard Meyer wrote:
> And I am still fighting with GIT in terms of producing Patches and
> reworking Patches, if, for example I later find an even "nicer" solution
> or continued testing shows up problems. Of course I read the man pages,
> read several articles about git, but they usually fail to explain the idea
> and inner working of a command. Sometimes commands have (for me) unexpected
> effects which are hard to undo.
> 
> As a custodian I sure would need more help and advice on how to handle
> certain situations. I would (for start) have to rely on advice from
> Wolfgang or someone else.

rebasing in my own branch tends to be how i manage my own changes.  this 
allows you to merge commits into one, change the order of things, edit changes 
in he middle of a tree, or drop commits.  but this is obviously for your own 
branches only and not for public branches other people are working off of.

i can probably answer most of your git related questions ... not sure if 
Wolfgang prefers them to be answered off list ...

> If, after considering my comments above, you still think you really need a
> custodian for AT91, I am game for it.

go for it
-mike
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 836 bytes
Desc: This is a digitally signed message part.
Url : http://lists.denx.de/pipermail/u-boot/attachments/20100805/90ff1f99/attachment.pgp 

  parent reply	other threads:[~2010-08-05 16:16 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-07-29  2:02 [U-Boot] ATMEL Custodians == /dev/null ?? Reinhard Meyer
2010-07-29  4:18 ` Mike Frysinger
2010-08-03 21:28   ` Wolfgang Denk
2010-08-05  9:14     ` Reinhard Meyer
2010-08-05 10:13       ` Andreas Bießmann
2010-08-05 10:44         ` Reinhard Meyer
2010-08-05 12:03       ` Eric Bénard
2010-08-05 16:16       ` Mike Frysinger [this message]
2010-08-05 18:27         ` Wolfgang Denk
2010-08-07  0:01         ` Reinhard Meyer
2010-08-07  0:20           ` Mike Frysinger
2010-08-07  0:58             ` Reinhard Meyer
2010-08-07  3:39               ` Mike Frysinger
2010-08-07 21:29                 ` Wolfgang Denk
2010-08-07 21:25           ` Wolfgang Denk
2010-08-07 21:24       ` Wolfgang Denk
2010-08-07 23:19         ` Reinhard Meyer
2010-08-07 23:44           ` Mike Frysinger
2010-08-08  0:07           ` Wolfgang Denk
2010-08-05 13:21     ` Bas Mevissen
2010-08-07 22:15 ` Mike Frysinger
2010-08-09  1:27   ` Haavard Skinnemoen
2010-08-09  5:59     ` Mike Frysinger
2010-08-09  6:29       ` Haavard Skinnemoen
2010-08-09  6:36         ` Mike Frysinger
2010-08-09  8:13         ` Wolfgang Denk
2010-08-09 11:13           ` Haavard Skinnemoen
2010-08-09 11:51             ` Wolfgang Denk
2010-08-09 15:48               ` Haavard Skinnemoen

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=201008051216.14165.vapier@gentoo.org \
    --to=vapier@gentoo.org \
    --cc=u-boot@lists.denx.de \
    /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