Hi Bostjan:
On Mon, Mar 21, 2011 at 6:14 PM, Bostjan Skufca bost...@a2o.si wrote:
Do you see a comparatively easy approach in SVN where original patch
just won't apply because code offsets were through the roof compared
to context included in a diff and manual page states you can't
increase
On Mon, Mar 21, 2011 at 6:14 PM, Bostjan Skufca bost...@a2o.si wrote:
Can you explain how it would have made your life easier for rebasing
code if we were using Git instead of SVN?
With git, my workflow would be:
- clone repo
- checkout tag 3.1.7
- apply external patch
- commit
- rebase to
Hi Bostjan:
Thanks for the patch, but could you please:
1) File a bug at http://bugzilla.ganglia.info
2) Re-base against trunk (development branch) and upload the patch as
an attachment:
https://ganglia.svn.sourceforge.net/svnroot/ganglia/trunk/monitor-core
3) You can also upload the original
Heh, my first reaction was He must be joking... :)
Anyway, done. However rebasing patches with SVN is major PITA and you
should consider yourself lucky that I persisted:)
Do you plan moving onto something better (hg, git)?
b.
On 21 March 2011 23:56, Bernard Li bern...@vanhpc.org wrote:
Hi
Hi Bostjan:
On Mon, Mar 21, 2011 at 5:16 PM, Bostjan Skufca bost...@a2o.si wrote:
Heh, my first reaction was He must be joking... :)
Anyway, done. However rebasing patches with SVN is major PITA and you
should consider yourself lucky that I persisted:)
Do you plan moving onto something
Can you explain how it would have made your life easier for rebasing
code if we were using Git instead of SVN?
First off - maybe because I am not a SVN expert. But my experience has
shown me that where I have had to struggle with SVN to manage
branches, individual commit cherry picks and
6 matches
Mail list logo
