From: "Ferry Huberts (Pelagic)" <ferry.huberts@pelagic.nl>
To: unlisted-recipients:; (no To-header on input)
Cc: Robin Rosenberg <robin.rosenberg.lists@dewire.com>,
"Shawn O. Pearce" <spearce@spearce.org>,
git <git@vger.kernel.org>
Subject: Re: [EGIT] How to deal with important modifications
Date: Sat, 28 Mar 2009 23:44:49 +0100 [thread overview]
Message-ID: <49CEA861.4070700@pelagic.nl> (raw)
In-Reply-To: <1238261528.6971.10.camel@localhost>
Yann Simon wrote:
> Hi,
>
> I am working on the synchronization view. It is not 100% functional yet.
> The view is not updated when a local file is modified for example.
> As the modifications are getting important, I was wondering how to deal
> with it. Should I continue my work an send all the patches when
> finished?
>
> To have an overview of the modifications:
> http://github.com/yanns/egit/commit/18c4a928d53345802a8c9641dcb2d457ebbe2cbc
> http://github.com/yanns/egit/commit/9fab398fa1b7b6efa9532b3c09e5bcfcc8bb9419
>
> Or should I begin to send patches, but by not activating the function
> yet?
> (It could be a way to have other people to help contributing.)
>
> Yann
Yann,
I was asking myself the same questions about my work on ignores and
chose to send it out early, being half completed. Don't know if that was
right, did not receive feedback yet, but it's only been 2 days with
Eclipsecon wrapping up on friday.
If you keep a seperate changeset in which you activate your work and
split up the changesets in manageable pieces it's easier for others to
review your work and comment on it.
Love to see your work though. Having the sync view available for git
would be a major plus. I proposed something simpler on the wiki: a
'pending changes' window. But if you have the complete sync view that's
wonderful.
my 2 cents :-)
Ferry
next prev parent reply other threads:[~2009-03-28 22:46 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-28 17:32 [EGIT] How to deal with important modifications Yann Simon
2009-03-28 22:44 ` Ferry Huberts (Pelagic) [this message]
2009-03-29 9:45 ` Robin Rosenberg
2009-03-30 4:30 ` Shawn O. Pearce
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=49CEA861.4070700@pelagic.nl \
--to=ferry.huberts@pelagic.nl \
--cc=git@vger.kernel.org \
--cc=robin.rosenberg.lists@dewire.com \
--cc=spearce@spearce.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.