Hi there dvcs users,
I am getting used to using git while working with upstream projects. So
when I try to make a patch available upstream, I encounter the following
problem: I want to make small commits during my work but of course send
the result as a single patch via git format-patch. So what's best:
1. clone upstream, create another local branch, work there, and then
merge that branchs changes via diff?
2. use <UNKNOWN_GIT_COMMAND> to merge those commits into a single one?
3. do not use intermdiate local commits (bad idea)
And the final question: When I got to the point of sending one single
patch and upstream merges it, how can I resync with upstream without
having to clone again?
Recently I started using some kernels built directly from Koji to test
out some hardware issues. So now I am mostly happily running 2.6.29-10
from a koji build. I'd like to provide feedback if its wanted on the
issues it has fixed for me, as well as some regressions I've noticed.
I'm not sure it warrants a bug as much as, installed and X now works, Y
doesn't, and a bug in Z resurfaced...
Is this a karma thing, or a bug thing, or just put it on the list thing?
Nathanael d. Noblet
Jeff Garzik has indicated in the merge review ticket
(https://bugzilla.redhat.com/show_bug.cgi?id=226367) that he has had
no interest in maintaining reiserfs-utils for some time and so I have
orphaned it for him. If someone wishes to maintain this package,
please feel free to pick it up but keep in mind that the merge review
linked above needs doing (which should be quite easy) and, though I'm
sure it's obvious to anyone who cares, that the package needs