Re: git-p4import.py robustness changes

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Simon Hausmann <simon@xxxxxx> wrote:
> On Thursday 14 June 2007 07:35:38 Shawn O. Pearce wrote:
> > I do appreciate you taking the time to use filter-branch to try to
> > cleanup this history a bit.  I really had originally planned on
> > pulling your tree through to my fastimport tree and then talking
> > Junio into merging with me.  But after reading through this history I
> > don't want do that, because of the oneline summaries I just pointed
> > out above, and because of the missing SBO.
...
> I have started cleaning up the history even more by reworking the log messages 
> of my commits (git-p4-enhanced-logs branch in fast-export, starting at the 
> last page). Once that is done (I expect that to take a few days) I'll add the 
> missing SOB lines with git-filter-branch and see if I can get an agreement 
> from Han-Wen and Marius for doing the same with their commits (adding the 
> missing lines).

OK.
 
> Would you be willing to reevaluate the situation regarding a merge once that's 
> done?

Absolutely.  I would like to see the git-p4 work in the main tree,
so it is more readily available to users, even though I'm not a p4
user myself.  ;-)

-- 
Shawn.
-
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html

[Index of Archives]     [Linux Kernel Development]     [Gcc Help]     [IETF Annouce]     [DCCP]     [Netdev]     [Networking]     [Security]     [V4L]     [Bugtraq]     [Yosemite]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Linux SCSI]     [Fedora Users]

  Powered by Linux