From: Denis Kenzior <denkenz@gmail.com>
To: ofono@ofono.org
Subject: Re: [PATCH 1/5] stk: Add parser for send ussd commands
Date: Sun, 20 Jun 2010 11:26:46 -0500 [thread overview]
Message-ID: <201006201126.47297.denkenz@gmail.com> (raw)
In-Reply-To: <CE761E84DADF2947A4AF22FB8D97A4731ED8E752@shsmsx501.ccr.corp.intel.com>
[-- Attachment #1: Type: text/plain, Size: 1172 bytes --]
Hi Yang,
> >Again, please watch out for this. If your patch touches something in two
> > or more directories of oFono, please send multiple patches.
>
> Thank you for applying the patches. But I have a question on this: Should
> we keep the code compile-able after each patch? Due to this consideration,
> I put those changes all in patch 2. This would sometimes be helpful when
> we want to investigate a regression after a bunch of patches. If this is
> not a requirement for this project, I will pay more attention on how to
> split the patches reasonably.
Keeping the code compilable is always preferable. For instance, if you're
adding a function to smsutil to use elsewhere, it is always preferable to have
a commit with this function and then commit(s) using this function.
However, there are cases when you're moving code around and breaking compile
in transient commits is unavoidable. In that case I still prefer clean,
logical patches. I will apply them all or not at all, so as long as the code
compiles & works cleanly afterward, it is fine.
Regards,
-Denis
>
> >Regards,
> >-Denis
>
> Regards,
> -Yang
>
prev parent reply other threads:[~2010-06-20 16:26 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-17 10:35 [PATCH 1/5] stk: Add parser for send ussd commands Yang Gu
2010-06-17 10:35 ` [PATCH 2/5] teststk: Add test for send ussd parser Yang Gu
2010-06-17 10:35 ` [PATCH 3/5] Modify " Yang Gu
2010-06-17 10:35 ` [PATCH 4/5] Refactor " Yang Gu
2010-06-21 14:18 ` Denis Kenzior
2010-06-17 10:35 ` [PATCH 5/5] stk: Add parser for timing advance objects Yang Gu
2010-06-18 19:04 ` [PATCH 1/5] stk: Add parser for send ussd commands Denis Kenzior
2010-06-20 13:52 ` Gu, Yang
2010-06-20 16:26 ` Denis Kenzior [this message]
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=201006201126.47297.denkenz@gmail.com \
--to=denkenz@gmail.com \
--cc=ofono@ofono.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.