On Sat, 27 Jul 2013 09:29:03 PM argonel wrote:
> Only if the branch itself is intended to be available to others, and only
> when you're ready for it to be publicly available to avoid accidents with
> `git push --all` etc.
I only checkout the readonly urls (anongit) to avoid just those disasters
On Sat, Jul 27, 2013 at 8:39 PM, Lindsay Mathieson <
lindsay.mathie...@gmail.com> wrote:
> If I'm working on a kde private local branch that is intended to eventually
> merge with master should I set it to track the remote master?
>
Only if the branch itself is intended to be available to others,
If I'm working on a kde private local branch that is intended to eventually
merge with master should I set it to track the remote master?
--
Lindsay
signature.asc
Description: This is a digitally signed message part.
>> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <
On Sat, 27 Jul 2013 10:19:09 AM Thomas Lübking wrote:
> Not trivially.
> Master might have progressed and differs from "my-branch"
> You'll then spam your patch with reverting all the stuff that has meanwhile
> been changed in master.
>
> -> First rebase your branch on (origin/)master, then the ab
On Sat, 27 Jul 2013 10:19:09 AM Thomas Lübking wrote:
> Not trivially.
> Master might have progressed and differs from "my-branch"
> You'll then spam your patch with reverting all the stuff that has meanwhile
> been changed in master.
Thanks Thomas
--
Lindsay
signature.asc
Description: This is
On Samstag, 27. Juli 2013 06:30:11 CEST, Lindsay Mathieson wrote:
I've made changes in a private branch and and want to create a
diff to submit
for application against master. Would this be the correct command?
git diff master..my-branch
Not trivially.
Master might have progressed and diff
On Saturday 27 July 2013 17:55:37 Lindsay Mathieson wrote:
> On Sat, 27 Jul 2013 09:46:23 AM Martin Graesslin wrote:
> > * review title
> > * review comment
>
> Don't see how they could be done automatically since its dependant on the
> actually patch. I usually have a range of commits to work wit
On Sat, 27 Jul 2013 09:46:23 AM Martin Graesslin wrote:
> * review title
> * review comment
Don't see how they could be done automatically since its dependant on the
actually patch. I usually have a range of commits to work with.
> post-review -g --branch=KDE/4.11 --parent=KDE/4.11 -o --userna
On Saturday 27 July 2013 16:49:41 Lindsay Mathieson wrote:
> On Sat, 27 Jul 2013 07:58:40 AM Martin Graesslin wrote:
> > In case it's about submitting to review board, please have a look at the
> > tool "post-review" [1] which is perfect for exactly this situation of
> > reviewing patches from a l
