New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

include export source in branchname #9

Open
eMBee opened this Issue Jul 29, 2015 · 3 comments

Comments

Projects
None yet
3 participants
@eMBee

eMBee commented Jul 29, 2015

if #8 is fixed to create a new independent branch, this would allow multiple exports to live in the same repo. since git is capable of handling that, it would be quite convenient. to help distinguish the branchen, we would then need more descriptive names:

export-to-git.pike /sources/ /tmp/export-test/

should create the branch sources-date or even <hostname>-sources-<date>

@eMBee eMBee added the export-to-git label Jul 29, 2015

@d4r3topk

This comment has been minimized.

Show comment
Hide comment
@d4r3topk

d4r3topk Jul 31, 2015

what about /home/coder/demo1.txt ? This should be -demo1.txt-date?

Also, keep in mind the long branch names, (sources-Jul-31-14-29-12-2015) or (root-sources-Jul-31-14-29-12-2015).

what about /home/coder/demo1.txt ? This should be -demo1.txt-date?

Also, keep in mind the long branch names, (sources-Jul-31-14-29-12-2015) or (root-sources-Jul-31-14-29-12-2015).

@eMBee

This comment has been minimized.

Show comment
Hide comment
@eMBee

eMBee Jul 31, 2015

as an alternative maybe use tags, and attach a note to the tag. name the tag with the path and a sequence number, ad add the date as a note attached to the tag:
http://git-scm.com/docs/git-notes

eMBee commented Jul 31, 2015

as an alternative maybe use tags, and attach a note to the tag. name the tag with the path and a sequence number, ad add the date as a note attached to the tag:
http://git-scm.com/docs/git-notes

@ajinkya007

This comment has been minimized.

Show comment
Hide comment
@ajinkya007

ajinkya007 Jun 10, 2016

Member

What we need here is a descriptive branch name. Tag would identify a specific commit with a special label, where as a typical use of notes is to supplement a commit message without changing the commit itself. Notes can be shown by git log along with the original commit message.
The git branch description command would allow us to add the description of the branch.

Member

ajinkya007 commented Jun 10, 2016

What we need here is a descriptive branch name. Tag would identify a specific commit with a special label, where as a typical use of notes is to supplement a commit message without changing the commit itself. Notes can be shown by git log along with the original commit message.
The git branch description command would allow us to add the description of the branch.

ajinkya007 added a commit that referenced this issue Aug 11, 2016

Merge pull request #9 from ajinkya007/Issue#14#19
Issue#14#19 Add utility to export-to-git script to support multiple source arguments.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment