include export source in branchname

[eMBee]

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>

[d4r3topk]

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]

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]

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.