[
https://issues.apache.org/jira/browse/LUCENE-6985?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15108520#comment-15108520
]
Uwe Schindler commented on LUCENE-6985:
---------------------------------------
bq. The list of steps above are one of the advantages of GIT - how to work on
multiple issues in parallel, without have multiple checkouts.
Oh not always!!! I tried to use a single GIT repo many times, but because of
the way my brain works and my daily workflow dictates (I often do several
things in parallel), I switched to multiple parallel ones every time. For my
personal work it is much easier to have separate checkout than all the time
switching with crazy command lines (or mouseclicks) just to quickly lookup a
file from another branch. The backside is of multiple repos: You have to
push/pull all the time to get those repos in sync. So is there any possibility
to have a single GIT repo but have more than one view on them in separate FS
directories and once I commit to any of them I don't need to push/pull? And
sorry, disk space is not an issue today, so I want to have 5 Lucene checkouts
in parallel :-)
> Create some (simple) guides on how to use git to perform common dev tasks
> -------------------------------------------------------------------------
>
> Key: LUCENE-6985
> URL: https://issues.apache.org/jira/browse/LUCENE-6985
> Project: Lucene - Core
> Issue Type: Task
> Reporter: Dawid Weiss
> Assignee: Dawid Weiss
>
> I'll prepare some simple github repos that demonstrate how to (from command
> line, GUI users can find their buttons I'm sure) perform:
> Simple tasks:
> 1. Checkout branch X, create local branch Y, modify something, create a diff
> for Jira.
> 2. Checkout branch X, create local branch Y, modify something, catch-up with
> changes on X, create a diff for Jira.
> 3. Checkout branch X, create local branch Y, modify something, catch-up with
> changes on X, apply aggregate changes from Y on X (as a single commit).
> 4. Backport feature/ commit C from branch X to Y via cherry picking.
> More advanced:
> 1. Create a feature branch off branch X, develop the feature, then apply it
> as a series of commits to X.
> 2. Create a feature branch off branch X, develop the feature, then apply it
> as a series of commits to X and Y (different branch).
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
