Martin Waitz wrote: ...Why the magic? The typical workflow in git is 1. You work on a branch, i.e. edit and commit and so on. 2. At some point, you decide to share the work you did on that branch (e-mail a patch, merge into another branch, push upstream or let it by pulled by upstream) I fail to understand why these two steps have to be mixed up. Someone care to explain? Regards Stephan - To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
| Ryan Hope | reiser4 for 2.6.27-rc1 |
| James Bottomley | Re: Integration of SCST in the mainstream Linux kernel |
| Andrew Morton | Re: 2.6.20-rc6-mm3 |
| Pierre Ossman | Re: [RFC][PATCH] cpuidle: avoid singing capacitors |
git: | |
| Johannes Schindelin | Re: rc4 - make quick-install-doc is broken |
| Johannes Schindelin | Re: Git benchmarks at OpenOffice.org wiki |
| Shawn O. Pearce | Re: Smart fetch via HTTP? |
| Ken Pratt | pack operation is thrashing my server |
| Chris | avoid logging useless ssh brute force attempts |
| Henning Brauer | Re: httpdv6 |
| Freddy DISSAUX | Re: acer aspire one dmesg? |
| stuartv | Re: Microsoft gets the Most Secure Operating Systems award |
| Jim Winstead Jr. | Re: Root Disk/Book Disk Compatibility |
| Stephen Pierce | SLS |
| Doug Evans | Re: Stabilizing Linux |
| Les Andrzejewski | X386/WD90C31/SUMSUNG SYNC MASTER 4 |
