Tim Niemueller, Thu, 28 Oct 2010 00:33:07 -0400:
> git clone package-repo
> make changes in package repo
> commit
> push repo somewhere
> send pull request to package maintainer
git format-patch(1)?
Matěj
--
http://www.ceplovi.cz/matej/, Jabber: mceplceplovi.cz
GPG Finger: 89EF 4BC6 288A BF43 1B
yersinia wrote:
> Beware also that git 1.7 by default enforce that it is not possible
> to push to a repository git "not bare", and, from my experience,
> many EPEL users don't haven't read the advice on this of the git
> manual - just an example of another possible "incompatibility"
Yep, but that
On Thu, Oct 28, 2010 at 5:01 PM, Todd Zullinger wrote:
> Tim Niemueller wrote:
> Incidentally, if you'd like to see an updated git for EL-5, point
> anyone you know that uses emacs-git my way. AFAIK, the only hang up
> to updating EPEL to git-1.7 is working out how to maintain the emacs
> suppor
Tim Niemueller wrote:
> Recently I wanted to modify a package. Since we now use git for
> packages, the following work flow feels natural:
>
> git clone package-repo
> make changes in package repo
> commit
> push repo somewhere
> send pull request to package maintainer
>
> Is that the anticipated w
Hi fellow Fedorans.
Recently I wanted to modify a package. Since we now use git for
packages, the following work flow feels natural:
git clone package-repo
make changes in package repo
commit
push repo somewhere
send pull request to package maintainer
Is that the anticipated workflow? Should I
