Request for improved commit tracking between fcoe and scsi trees

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

 



James, Robert-
	I've been doing lots of backports of FCoE code to the RHEL tree these
last few months, and I've noticed something fairly irritating, and I was
wondering if you two could help me out with it (in fact you two are the only two
which can).  I noticed that commits which are accepted into the FCoE tree that
get passed upstream through the scsi tree have their commit hashes altered.  I
can't find any examples currently, due to the fact that you, Robert, have
recently re-cloned your git tree at open-fcoe.org, so all this nastiness has
been covered up currently, but if things don't change, this issue will quickly
resurface.

Regardless, This makes it _really_ difficult to track a given patchs' traversal 
between trees upstream, and makes my life as a distro subsystem maintainer fairly
painful.  Normally I would just live with it, but I can't see any reason why it
should be this way, given that git can easily prevent this with a pull.  James,
Robert, could you two please work out a way to provide commit hash consistency
between your trees?  It would make mine (and I'm sure many other people's)
lives, much easier.

Thanks & Regards
Neil

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


[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Index of Archives]     [SCSI Target Devel]     [Linux SCSI Target Infrastructure]     [Kernel Newbies]     [IDE]     [Security]     [Git]     [Netfilter]     [Bugtraq]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Linux ATA RAID]     [Linux IIO]     [Samba]     [Device Mapper]
  Powered by Linux