Login or Register to Ask a Question and Join Our Community

Sponsored Content
Full Discussion: Cyberspace Situation Graphs - Cyberspace Situational Awareness
The Lounge What is on Your Mind? Cyberspace Situation Graphs - Cyberspace Situational Awareness Post 302982091 by Neo on Friday 23rd of September 2016 08:08:39 AM
Old 09-23-2016
Update:

Now we have one very experienced collaborator for this project from ResearchGate; he is PhD student who is planning on writing his PhD these around this topic.

Keywords: cyberspace situational awareness, cyberspace situation graph, cyberspace object base (cyber object base), cyberspace situation base (cyber situation base), cyber-object, parent cyber-object, child cyber-object, device cyber-clone
 

7 More Discussions You Might Find Interesting

1. What is on Your Mind?

Cyberspace Situational Awareness - End of Year Research Update

Here is an end-of-year update of my CSA research for 2016. A BIG THANK YOU to everyone at unix.com who keeps the forums running so well as I write code for cyberspace situational awareness experiments and do my research. I am still hopelessly trying to save the world from the unintended... (6 Replies)
Discussion started by: Neo
6 Replies

2. What is on Your Mind?

Calculating Warp Coordinates in Cyberspace - Cyberspace Situational Awareness

Please message me or post in this thread if anyone is interested in contributing some C, C++, or C# code for this project. Right now we have an open source C++ git project (created by someone else a few years ago) that fails when we try to compile on Ubuntu. I need someone to fix the make... (4 Replies)
Discussion started by: Neo
4 Replies

3. What is on Your Mind?

A Journey Into Cyberspace

A Journey Into Cyberspace A brief visual presentation on the results of research and development into new visualization tools and methods for cyberspace situational awareness via graph processing and multisensor data fusion. https://www.unix.com/members/1-albums112-picture678.png ... (1 Reply)
Discussion started by: Neo
1 Replies

4. What is on Your Mind?

Application for Virtualizing CyberSpace like Outer Space for Cyberspace Situational Awareness

Richard Zuech annotates his first experience flying in virtualized cyberspace hunting the bad guys! ... and he finds some! Application for Virtualizing CyberSpace like Outer Space for Cyberspace Situational Awareness (0 Replies)
Discussion started by: Neo
0 Replies

5. What is on Your Mind?

Virtualized Cyberspace, Cyberspace Consciousness and Simulation Theory - What Do You Think?

What do you think? Read this: Virtualized Cyberspace, Cyberspace Consciousness and Simulation Theory and comment below.... Are we in a computer simulation? Yes or No? Thanks! (0 Replies)
Discussion started by: Neo
0 Replies

6. What is on Your Mind?

Virtualized Cyberspace - Visualizing Patterns & Anomalies for Cognitive Cyber Situational Awareness

Our team just published this technical report on ResearchGate: Virtualized Cyberspace - Visualizing Patterns & Anomalies for Cognitive Cyber Situational Awareness ABSTRACT ACKNOWLEDGMENTS Creative Commons Attribution-NonCommercial-ShareAlike 4.0 International Public License This... (0 Replies)
Discussion started by: Neo
0 Replies

7. What is on Your Mind?

Back to Cyber Situational Awareness Software Development

After mulling over self-publishing a cyberspace situational awareness mini-series starting with a short book on human cyber consciousness, I think it is best I delay writing a book and focus on software development. The general idea of human cyber consciousness is indirectly discussed in this... (0 Replies)
Discussion started by: Neo
0 Replies

LEARN ABOUT LINUX

git-cherry

GIT-CHERRY(1)							    Git Manual							     GIT-CHERRY(1)

NAME

       git-cherry - Find commits yet to be applied to upstream

SYNOPSIS

       git cherry [-v] [<upstream> [<head> [<limit>]]]

DESCRIPTION

       Determine whether there are commits in <head>..<upstream> that are equivalent to those in the range <limit>..<head>.

       The equivalence test is based on the diff, after removing whitespace and line numbers. git-cherry therefore detects when commits have been
       "copied" by means of git-cherry-pick(1), git-am(1) or git-rebase(1).

       Outputs the SHA1 of every commit in <limit>..<head>, prefixed with - for commits that have an equivalent in <upstream>, and + for commits
       that do not.

OPTIONS

       -v
	   Show the commit subjects next to the SHA1s.

       <upstream>
	   Upstream branch to search for equivalent commits. Defaults to the upstream branch of HEAD.

       <head>
	   Working branch; defaults to HEAD.

       <limit>
	   Do not report commits up to (and including) limit.

EXAMPLES

   Patch workflows
       git-cherry is frequently used in patch-based workflows (see gitworkflows(7)) to determine if a series of patches has been applied by the
       upstream maintainer. In such a workflow you might create and send a topic branch like this:

	   $ git checkout -b topic origin/master
	   # work and create some commits
	   $ git format-patch origin/master
	   $ git send-email ... 00*

       Later, you can see whether your changes have been applied by saying (still on topic):

	   $ git fetch	# update your notion of origin/master
	   $ git cherry -v

   Concrete example
       In a situation where topic consisted of three commits, and the maintainer applied two of them, the situation might look like:

	   $ git log --graph --oneline --decorate --boundary origin/master...topic
	   * 7654321 (origin/master) upstream tip commit
	   [... snip some other commits ...]
	   * cccc111 cherry-pick of C
	   * aaaa111 cherry-pick of A
	   [... snip a lot more that has happened ...]
	   | * cccc000 (topic) commit C
	   | * bbbb000 commit B
	   | * aaaa000 commit A
	   |/
	   o 1234567 branch point

       In such cases, git-cherry shows a concise summary of what has yet to be applied:

	   $ git cherry origin/master topic
	   - cccc000... commit C
	   + bbbb000... commit B
	   - aaaa000... commit A

       Here, we see that the commits A and C (marked with -) can be dropped from your topic branch when you rebase it on top of origin/master,
       while the commit B (marked with +) still needs to be kept so that it will be sent to be applied to origin/master.

   Using a limit
       The optional <limit> is useful in cases where your topic is based on other work that is not in upstream. Expanding on the previous example,
       this might look like:

	   $ git log --graph --oneline --decorate --boundary origin/master...topic
	   * 7654321 (origin/master) upstream tip commit
	   [... snip some other commits ...]
	   * cccc111 cherry-pick of C
	   * aaaa111 cherry-pick of A
	   [... snip a lot more that has happened ...]
	   | * cccc000 (topic) commit C
	   | * bbbb000 commit B
	   | * aaaa000 commit A
	   | * 0000fff (base) unpublished stuff F
	   [... snip ...]
	   | * 0000aaa unpublished stuff A
	   |/
	   o 1234567 merge-base between upstream and topic

       By specifying base as the limit, you can avoid listing commits between base and topic:

	   $ git cherry origin/master topic base
	   - cccc000... commit C
	   + bbbb000... commit B
	   - aaaa000... commit A

SEE ALSO

       git-patch-id(1)

GIT

       Part of the git(1) suite

Git 1.8.5.3							    01/14/2014							     GIT-CHERRY(1)
All times are GMT -4. The time now is 05:36 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy