From: Lea Wiemann <lewiemann@gmail.com>
To: Petr Baudis <pasky@suse.cz>
Cc: git@vger.kernel.org, Junio C Hamano <gitster@pobox.com>
Subject: Merging strategy for extending Git.pm (was: [PATCH] perl/Git.pm: add rev_parse method)
Date: Fri, 30 May 2008 17:15:21 +0200 [thread overview]
Message-ID: <48401A09.6060301@gmail.com> (raw)
In-Reply-To: <20080530095938.GE18781@machine.or.cz>
Petr Baudis wrote:
> (i) Tell Junio you would like the changes to stay in pu or next for now.
> [...]
> you will be getting immediate feedback about your changes as you go and
> your work will be useful at any point of time.
Junio, any comments on this? Doing doing small iterations is great IMO,
and I'll be doing it in any case. However, right now I see three
possible problems with merging to pu continuously (rather than keeping
it on my branch and merging in large chunks):
1. I'm working full-time on this, so I might produce patches that
loosely depend on one another at a peak rate of 2-3 per day. (I can do
other project-related stuff while my patches are waiting for review, but
only so much of course.) Do you have any experience with working with
full-time developers on Git? Do you see problems with my potentially
high patch frequency?
2. I'll be changing my own API. In other words, the API is really
unstable while I work on this (with the only user of the API being
Gitweb, which I'll update as I go). Is that OK for the pu branch?
3. I try to be careful with my commits, but it might still cause more
work for whoever reviews my patches, compared to reviewing larger
chunks. (That's because some of the stuff I write might end up being
deleted or rewritten later.)
Apart from that, I think merging (and getting feedback) continuously is
great.
So, comments would be much appreciated!
-- Lea
next prev parent reply other threads:[~2008-05-30 15:16 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-30 4:43 [PATCH] perl/Git.pm: add rev_parse method Lea Wiemann
2008-05-30 7:03 ` Lea Wiemann
2008-05-30 9:59 ` Petr Baudis
2008-05-30 15:15 ` Lea Wiemann [this message]
2008-05-30 23:20 ` Merging strategy for extending Git.pm Junio C Hamano
2008-05-31 11:38 ` Merging strategy for extending Git.pm (was: [PATCH] perl/Git.pm: add rev_parse method) Johannes Schindelin
2008-05-31 12:42 ` Merging strategy for extending Git.pm Lea Wiemann
2008-05-31 12:52 ` Johannes Schindelin
2008-05-30 20:28 ` [PATCH] perl/Git.pm: add rev_parse method Junio C Hamano
2008-05-30 9:50 ` Petr Baudis
2008-05-30 20:27 ` [PATCH] perl/Git.pm: add parse_rev method Lea Wiemann
2008-05-30 21:05 ` Petr Baudis
2008-05-30 21:25 ` Junio C Hamano
2008-05-30 21:44 ` Randal L. Schwartz
2008-05-30 21:59 ` Lea Wiemann
2008-05-30 22:03 ` Randal L. Schwartz
2008-05-30 22:05 ` Lea Wiemann
2008-05-30 22:19 ` Junio C Hamano
2008-05-31 11:50 ` Johannes Schindelin
2008-05-31 12:17 ` Support for old Perl versions Petr Baudis
2008-05-31 12:32 ` Johannes Schindelin
2008-05-30 21:49 ` [PATCH] perl/Git.pm: add parse_rev method Petr Baudis
2008-05-31 13:52 ` [PATCH v2] " Lea Wiemann
2008-06-01 3:17 ` [PATCH v3] " Lea Wiemann
2008-06-01 3:17 ` Lea Wiemann
2008-06-01 17:38 ` Lea Wiemann
2008-06-01 21:54 ` Miklos Vajna
2008-06-01 22:51 ` Lea Wiemann
2008-06-02 4:59 ` Junio C Hamano
2008-06-02 13:51 ` Lea Wiemann
2008-06-01 23:09 ` [PATCH v4] perl/Git.pm: add get_hash method Lea Wiemann
2008-06-01 23:24 ` Lea Wiemann
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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=48401A09.6060301@gmail.com \
--to=lewiemann@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=pasky@suse.cz \
/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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).