Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
O
ORG.Asm
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 19,166
    • Issues 19,166
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Merge Requests 0
    • Merge Requests 0
  • Operations
    • Operations
    • Incidents
  • Analytics
    • Analytics
    • Repository
    • Value Stream
  • Wiki
    • Wiki
  • Members
    • Members
  • Collapse sidebar
  • Activity
  • Graph
  • Create a new issue
  • Commits
  • Issue Boards
  • ORG.Asm
  • ORG.Asm
  • Issues
  • #30

Closed
Open
Opened Mar 17, 2016 by Eric Coissac@coissacOwner

A new way for managing seeds with the --seeds option in buildgraph

In relation with issue #27 (closed), the --seeds option have to change its behavior.

If the --seeds <SEEDNAME> option is added to the buildgraph command, the new seed set is added to the seed set collection and put the new seeds in the stack for the first graph extension step.

if the --seeds <SEEDNAME> is used in conjunction with the --clean option (#27 (closed)) , all the previous seed sets are erased

Assignee
Assign to
A new buildgraph command
Milestone
A new buildgraph command
Assign milestone
Time tracking
None
Due date
None
Reference: org-asm/org-asm#30